Apparatus and methods for management, configuration and provisioning of communication devices in a distributed access architecture

ABSTRACT

Apparatus and methods for configuration of a Remote PHY or Communications Device, and redirection one or more core device(s) within a content and data delivery network. In one embodiment, the architecture comprises a Remote PHY distributed CCAP architecture within a cable network, and the methods and apparatus provide a network operator with the ability to associate multiple remote devices (and their associated service groups, and hence subscribers) to one or more specific CCAP core(s), to facilitate the operator&#39;s operational and support models, including defining and instantiating an overall network topology. In one exemplary variant, information from multiple sources are used by an analytics engine to calculate remote device-to-core assignments, so as to achieve the desired overall operational topology and goals. Improved mechanisms for remote device installation are described. In one implementation, mobile devices are used by installers to interact with the assignment process logic.

PRIORITY

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/529,881 entitled “APPARATUS AND METHODS FOR MANAGEMENT,CONFIGURATION AND PROVISIONING OF COMMUNICATION DEVICES IN A DISTRIBUTEDACCESS ARCHITECTURE” filed Jul. 7, 2017, and incorporated herein byreference in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of data networksand wireless devices, and specifically in one exemplary aspect to anarchitecture which integrates or unifies provision of high-speed dataservices in a variety of different locations and use cases.

2. Description of Related Technology

The continued growth of Internet traffic has driven Cable operators toevolve their network architectures and data service technologies. HybridFiber-coaxial (HFC) is the physical layer architecture for Cableoperators, and the Data Over Cable Services Interface Specification(DOCSIS) standard is the primary technology used by Cable operators totransfer data over HFC.

As the name implies, an HFC network 100 combines fiber optical cablesand coaxial cables to distribute signals between the MSO (e.g., cable)operator's facilities and the subscriber's location as shown in FIG. 1.Specifically, electrical signals (e.g. TV channels or Internet traffic)generated or issued by the headend 102 are converted into opticalsignals (light) at one or more distribution hub facilities 104, sentover the fiber optical cables 106 to optical nodes 108, which thenconvert the light signals back to the electrical signals, and send themover the coaxial cables 110 to the user's or subscriber's location orpremises 112. At the subscriber's location the electrical signals arereceived by Customer Premise Equipment (CPE) such as Set-top Boxes (STB)or Cable Modems (CM) or gateways. For two-way services, such as Internetaccess, the process is reversed for upstream signals (i.e. signals fromthe subscriber to the operator's facilities). One major advantage of HFCis that signals can be sent much longer distances over the optical fibercables 106 without regeneration/amplification, as compared to coaxialcables 110. The evolution from a pure coaxial architecture to an HFCarchitecture allowed, inter alia, cable operators to increase theirservice area while limiting the number of distribution hub facilities.

DOCSIS and CCAP

The DOCSIS standards specify the systems and mechanisms used todistribute data services over HFC. As used herein, the term “DOCSIS”refers to any of the existing or planned variants of the Data Over CableServices Interface Specification, including for example DOCSIS versions1.0, 1.1, 2.0, 3.0 and 3.1. Initial versions of DOCSIS specified twoprimary systems—the Cable Modem Termination Subsystem (CMTS) and theCable Modem (CM), not shown. The CMTS is typical located a distributionhub 104 and is responsible for data communications between the CM at auser's or subscriber's location (e.g. their home) 112 and a data service(e.g. Internet access). The CMTS converts data packets between the dataservice located on the transport ring/network and the correspondingsignals distributed over the HFC network 100. The CM converts datapackets between subscriber's Local Area Network (LAN) and thecorresponding signals distributed over the HFC network.

For example, packets from the Internet data service can enter thetransport ring 103 via a Router, arrive at CMTS which converts/modulatesthem into appropriate signals for transmission over the HFC network. Thesignals are received by a CM at the subscriber's location,converted/demodulated back into packets and sent to the subscriber'sdevice, e.g., attached to their LAN. Later version of the DOCSISstandard include digital video support into the CMTS and creation of anew platform commonly known as the Converged Cable Access Platform(CCAP), as described in later detail subsequently herein.

There are several mechanisms employed by MSOs such as Cable Operators toincrease capacity of their data services. As used herein, the terms“MSO” or “multiple systems operator” refer to a cable, satellite, orterrestrial network provider having infrastructure required to deliverservices including programming and data over those mediums. Thesemechanisms include, but are not limited to: segmentation, spectrumupgrades, spectrum planning/allocations, and spectral efficiency.

Segmentation broadly involves adding more optical nodes 108, whichin-turn decrease the number of subscribers or users sharing the capacityon a given segment of the HFC network. Segmentation (sometime called“node-splits”) typical requires the operator to deploy fiber cablesdeeper into their service, so that the added optical nodes can belocated closer to the users/sub scribers.

Transmission of signals over HFC employees Frequency DivisionMultiplexing (FDM). The total available Radio Frequency (RF) spectrumdefines the total capacity for a given segment. By upgrading HFCtransmission technology (lasers, amplifiers, taps, CPE, etc.), operatorscan increase the total available RF spectrum and hence the totalavailable capacity. For example, with the latest transmissiontechnology, operators can achieve 1.2 GHz of spectrum, broader than thehistorical roughly 800 MHz of usable spectrum under typical prior cablesystems.

The data capacity derived from the available RF spectrum depends on,among other things, the modulation techniques and noise mitigationcapabilities of the transmission technology. The amount of informationthat can be transmitted using a given amount of spectrum is oftenreferred to as “spectral efficiency,” and is typical measured in databits/Hz. DOCSIS has continued to increase its spectral efficiency byadopting new modulation techniques such as OFDM and new error correctionmechanisms, namely LDPC.

While the foregoing techniques have allowed operators to scale extantcapacity, the current HFC and DOCSIS architectures present a set ofchallenges to further increases. For example, segmentation will drive asignificant increase in the number of CMTS/CCAP devices, which willeventually exhaust the space, power and HVAC capacity of thedistribution facilities. Moreover, HFC employees Amplitude Modulation(AM) of lasers to transmit the RF spectrum signals over the fiberoptical cables (after conversion to the optical domain). This is typicalreferred to as “analog optics.” The inherent transmissioncharacteristics of analog optics (e.g. signal-to-noise, path loss, etc.)limit the ability to increase spectral efficiency. Yet other limitationsare present.

In response to these challenges a new DOCSIS architecture has beendeveloped called the Distributed Access Architecture (DAA). TheDistributed Access Architecture (DAA) replaces the analog optics betweenthe aforementioned CMTS/CCAP devices and the optical nodes 108 with“digital optics” that use baseband transmission such as Ethernet.Furthermore, DAA moves some of the DOCSIS function to the optical node108. The current version of the DOCSIS specification also moves the PHYlayer (including modulation/demodulation to a new node referred to as a“Remote PHY Device” (RPD). See, inter alia, CableLabs “Data-Over-CableService Interface Specifications DCA Distributed CCAP ArchitecturesOverview Technical Report CM-TR-DCA-V01-150908,” incorporated herein byreference in its entirety. In this architecture, the centralizedCCAP/CMTS functionality has been replace by a CCAP Core or Controller inthe “distributed” portion of the architecture, depending on thearchitecture variant selected (e.g., Remote MAC+PHY, Split-MAC, orRemote PHY). One consequence of this approach is that non-remoteCCAP/CMTS functions can implemented as software functions in e.g., avirtualized computing platform.

RPD Initialization Process

During the RPD initialization process, the RPD and other system/networkelements execute a series of steps after RPD power-up, thereby enablingthe RPD to become fully operational. As shown in the examplearchitecture of FIG. 2, in addition to normal DOCSIS signaling betweenthe CCAP Core 202 and the relevant cable modem(s) 206, the RPD 204 and agiven CCAP Core 202 communicate via three different protocols 203,namely:

(i) R-DEPI (Remote Downstream External PHY Interface)—This interfacehandles downstream communications between the given CCAP Core and theRPD. Per Cable Labs, it is characterized as an “IP pseudowire” betweenthe MAC and PHY in an MHAv2 system that comprises both a data path forDOCSIS data frames, video data packets, and OOB (out of band) packets,as well as a session control path. MHAv2 retains the original MPT(MPEG-TS) encapsulation of MHAv1 (for backward compatibility), but alsoutilizes MPEG encapsulation (MCM or Multi-channel MPEG). MHAv2 alsorequires support of a PSP (Packet Streaming Protocol) mode, such as tosupport expansion of services under DOCSIS 3.1.

(ii) R-UEPI (Remote Upstream External PHY Interface)—This interfacesupports upstream communications between the RPD and the CCAP Core. Aswith R-DEPI, it is referred to as an IP pseudowire between the PHY andMAC within an MHAv2 system that provides a data path for DOCSIS frames,as well as a control path for communication sessions.

(iii) The GCP (Generic Control Plane)—The Generic Control Plane isdescribed in the Cable Labs Specification, CM-SP-GCP-I02-160512, May 12,2016, (and any subsequent versions) incorporated herein by reference inits entirety. Per CM-SP-GCP-I02-160512, the GCP provides a control plane“tunnel” over a generic, reliable transport protocol such as TCP. GCP ineffect mimics functionality that exists over a hardware bus (e.g.,between a digital CPU and a peripheral interface IC), and can accessregister or use higher layer data structures to effect data read/writeoperations. Functions controlled via GCP include device reset,power-up/power-down, and hardware interrupts. As such, GCP allows ICs orother embedded entities to communicate across a network interface suchas an Ethernet (IEEE Std. 802.3) PHY.

Solutions Needed

In the traditional integrated CCAP architecture discussed above, theDOCSIS network topology (MAC domain or service group) is mapped to anHFC service group when the integrated CCAP ports (downstream andupstream) are wired to the Optical HFC Nodes servicing a particulargeographic area. This mapping binds all the physical network elements(e.g. CCAP/CMTS, cable modems, outside plant, HFC amplifiers, etc.) andlogical networks (e.g., DOCSIS MAC domains) into an overall networktopology that supports subscribers in that specific geographic area(i.e., a service group). Cable system operations and support is heavilydependent on the ability to link a subscriber or set of subscribers ofan operator's HFC network to the physical and logical. elements. Forexample, if a subscriber or group of subscribers in given service groupis having a network-related problem (as opposed to for example issueswith their particular CPE), the network operator needs to be able toidentify all of the physical and logical elements in the path forservice delivery to the affected subscriber(s). Conversely, if theoperator is making a change to a physical or logical element, it isdesirous to be able to identify all the subscribers and/or otherelements in the service delivery path, so that the operator mayproactively plan, support and communicate any service delivery impacts.

In a CCAP “Remote PHY” Distributed Access Architecture, a new anddifferent set of logical and physical elements exists within the pathfor services delivery. An RPD is physically wired to a service group(effectively becoming the aforementioned “optical node” counterpart),and connected to an IP network for communications with one or more CCAPCores. The association of RPDs to CCAP Cores is logical; the CCAPCore(s) merely see an RPD as an IP device (a trusted device) attachedover the IP network. Furthermore, CCAP Cores can exist as virtualizedsoftware elements running in any one of a multitude of data centersconnected to the IP network.

Accordingly, such new remote or “distributed” architectures result in abroad spectrum of new logical and physical network topologies used forservice delivery as compared to prior art technology. Despite theforegoing extant CCAP capabilities and interfaces, control andconfiguration of each particular RPD within such new remote ordistributed architectures, the complexity of instantiating an overallnetwork topology that implements the prescribed operator operational andsupport model is greatly increased, and further is prone to any numberof different errors, due to the many possible combinations orpermutations of the distributed elements, including both physically andlogically.

Yet further, the installation of such distributed topology componentssuch as RPDs can involve a manual process, and may encounter issuesduring installation requiring resolution by the installer.

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for management, configuration andprovisioning of communication devices in a distributed accessarchitecture, including for network component assignment andredirection/reassignment.

In a first aspect of the disclosure, a method of operating a distributednetwork is described. In one embodiment, the method includes:identifying at least one remote entity, the at least one remote entitycomprising physical layer (PHY) apparatus for communication with one ormore user devices; obtaining data from the at least one remote entity;providing the obtained data to a computerized analytics process; basedat least on (i) the provided obtained data, and (ii) data relating toone or more network operational policies, calculating an allocation ofthe at least one remote entity to at least one core entity within thedistributed architecture network; and based at least on the calculatedallocation, causing the at least one remote entity to associate with theat least one core entity during operation of the distributedarchitecture network.

In another aspect, a method of processing an initialization requestwithin a core entity of a distributed architecture digital network isdisclosed. In one embodiment, the method includes: receiving aninitialization message from a remote device within the distributedarchitecture digital network; authenticating at least the remote device;establishing a communication interface between the remote device and thecore entity; determining a first status of the remote device; based onthe determination of the first status, causing the remote device to usethe core entity as its operational core; notifying an installationprocess of the availability of the remote device for configuration;receiving data from the installation process relating to theconfiguration of the remote device; using the received data to remotelyconfigure the remote device; designate the remote device as availablefor redirection to another core entity within the network; and causingre-initialization of the remote device, the re-initialization causingthe remote device to utilize the another core entity as its operationalcore.

In another aspect of the disclosure, a CCAP Core apparatus is disclosed.In one embodiment, the CCAP Core apparatus includes an enhanced Core(eCore) configured to selectively utilize analyses by a networkanalytics process to determine optimized device allocations within adesired network topology or performance framework.

In another aspect of the disclosure, a CCAP RPD apparatus is disclosed.In one embodiment, the CCAP RPD apparatus includes an enhanced RPD(eRPD) configured to selectively provide data to one or more Coreentities and/or network analytic processes, and to receive configurationdata from one or more of the Core entities, to enable optimizedassignment of the eRPD within the network topology.

In a further aspect of the disclosure, a distributed architecturenetwork system is disclosed. In one embodiment, the system includes: (i)one or more eCore apparatus, and (ii) one or more eRPD apparatus in datacommunication with at least one of the eCore apparatus.

In a further aspect, a configuration, reconfiguration and assignmentprotocol is disclosed. In one embodiment, the protocol is adapted foruse in a CCAP-enabled distributed network, and includes datacommunications between one or more eRPDs, eCores, and an analyticsengine to communicate data relevant to assignment/re-assignment of eRPDsto one or more eCores. In one variant, the protocol implements a GCP(generic control plane) interface modified to include data relating tothe one or more eRPDs (e.g., to write data such as a Device Alias valueinto a target RPD).

In another aspect, an analytics engine is disclosed. In one embodiment,the analytics engine comprises a computerized process operable to run onone or more network entities (e.g., one or more head-end servers, ordistributed entities such as CCAP eCores) and to analyze data relatingto RPDs within the network, and specified operational policies andrequirements, to determine optimized RPD-to-Core allocations.

In a further aspect, a computer-readable apparatus is disclosed. In oneembodiment, the apparatus includes a storage medium having at least onecomputer program disposed thereon in the form of a plurality ofcomputer-executable instructions. In one variant, the apparatus is ahard disk drive (HDD). In another variant, the apparatus is a solidstate device (SSD). In another variant, the apparatus comprises aprogram memory device.

In another aspect of the disclosure, computerized logic for implementingselective remote device configuration and assignment is disclosed. Inone embodiment, the logic is embodied as software (e.g., one or morecomputer programs). In another embodiment, the logic is embodied asfirmware. In another embodiment, the logic is embodied as part of a FPGAor other gate array. In yet another embodiment, the logic is embodied aspart of an application-specific IC (ASIC).

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary prior art hybridfiber (HFC) network configuration.

FIG. 2 is a block diagram illustrating an exemplary prior art CCAP-basedarchitecture for use in the HFC network of FIG. 1.

FIG. 3 is a block diagram illustrating an exemplary embodiment of aCCAP-based architecture implementing various aspects of the presentdisclosure.

FIG. 4 is a logical flow diagram illustrating a prior art initializationprocess as described in CM-SP-R-PHY-I06-170111.

FIG. 5 is a logical flow diagram illustrating a prior art process forconnection to a Principal CCAP Core as described inCM-SP-R-PHY-I06-170111.

FIG. 6 is a ladder diagram illustrating a prior art keep-alive processas described in CM-SP-R-PHY-I06-170111.

FIG. 7 is a logical flow diagram illustrating an exemplary embodiment ofa CCAP network communication processing method according to the presentdisclosure.

FIG. 8 is a logical flow diagram illustrating a second exemplaryembodiment of a CCAP network communication processing method accordingto the present disclosure, wherein the relevant RDP/eRDP supports aredirection post-configuration via the GCP interface.

FIG. 9 is a graphical illustration of a logical grouping of OperationalCCAP Cores/eCores and associated metadata according one embodiment ofthe disclosure.

FIG. 10 is a logical block diagram illustrating an exemplary CCAP-basedarchitecture consistent with the methods of FIGS. 7 and 8, andinterrelationships of the components thereof, according to the presentdisclosure.

FIG. 11 is a logical flow diagram illustrating another exemplaryembodiment of a CCAP network communication processing method accordingto the present disclosure.

FIG. 12 is a logical flow diagram illustrating yet another exemplaryembodiment of a CCAP network communication processing method accordingto the present disclosure, wherein the relevant RDP/eRDP supports aredirection post-configuration via the GCP interface.

FIG. 13 is a logical block diagram illustrating an exemplary CCAP-basedarchitecture consistent with the methods of FIGS. 11 and 12, andinterrelationships of the components thereof, according to the presentdisclosure.

FIG. 14 is a logical flow diagram illustrating another exemplaryembodiment of a CCAP network communication processing method forRPDs/eRPDs that do not require additional configuration data from theinstaller, according to the present disclosure.

FIGS. 15A and 15B are logical block diagrams illustrating otherexemplary CCAP-based architectures and interrelationships of thecomponents thereof (including the ability of the external system(s) usedby the Default CCAP to interact with the systems used to manage theOperational CCAP Cores/eCores), according to the present disclosure.

FIG. 16 is a graphical representation of an exemplary embodiment of ananalytics engine calculation according to the present disclosure.

FIGS. 3 and 7-16 © Copyright 2017-2018 Howard Pfeffer. All rightsreserved. All other figures Copyright © of their respective copyrightholders.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “application” and “application computerprogram” refer generally and without limitation to a unit of executablesoftware that implements a certain functionality or theme. The themes ofapplications vary broadly across any number of disciplines and functions(such as on-demand content management, e-commerce transactions,brokerage transactions, home entertainment, calculator etc.), and oneapplication may have more than one theme. The unit of executablesoftware generally runs in a predetermined environment; for example, theunit could include a downloadable Java Xlet™ that runs within theJavaTV™ environment.

As used herein, the term “client device” includes, but is not limitedto, set-top boxes (e.g., DSTBs), gateways, modems, personal computers(PCs), and minicomputers, whether desktop, laptop, or otherwise, andmobile devices such as handheld computers, PDAs, personal media devices(PMDs), tablets, “phablets”, and smartphones.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

The term “Customer Premises Equipment (CPE)” refers without limitationto any type of electronic equipment located within a customer's orsubscriber's premises and connected to or in communication with anetwork.

As used herein, the term “headend” refers generally to a networkedsystem controlled by an operator (e.g., an MSO) that distributesprogramming to MSO clientele using client devices. Such programming mayinclude literally any information source/receiver including, inter alia,free-to-air TV channels, pay TV channels, interactive TV, and theInternet.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, WAP, SIP, UDP, FTP, RTP/RTCP, H.323, etc.).

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “Wi-Fi” and ‘WLAN” refers to, withoutlimitation, any of the variants of IEEE-Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac or 802.11-2012.

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A,WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20,Zigbee®, Z-wave, narrowband/FDMA, OFDM, PCS/DCS, LTE/LTE-A, analogcellular, CDPD, satellite systems, millimeter wave or microwave systems,acoustic, and infrared (i.e., IrDA).

Overview

The present disclosure comprises, inter alia, a set of systems,apparatus, and methodologies to configure an RPD (or a RemoteCommunications Device) and redirect it to another CCAP Core/s based on aset of rules and data.

Specifically, under an exemplary Remote PHY distributed architecture, itis desirous for a network operator to have the ability to associatemultiple RPDs (and their associated service groups, and hencesubscribers) to one or more specific CCAP Core(s) or set of Cores, inorder to facilitate the operator's operational and support models(including defining and instantiating an overall network topology, withall of the physical and logical elements in the path(s) of servicedelivery). The various aspects of the present disclosure advantageouslyprovide such capabilities, including via enhanced CCAP Cores (eCores)and RPDs (eRPDS), as well as an analytics engine.

In one exemplary embodiment, information from multiple sources (theRPDs/eRPDs and CCAP Cores/eCores within the network, external systemsand an installer) are used by the analytics engine to calculateRPD/eRPD-to-Core/eCore assignments, so as to achieve the desired overalloperational topology and goals. In addition to the topologyconfiguration analytics engine, improved mechanisms for RPD/eRPDinstallation are described. In one implementation, mobile devices areused by installers to interact with the assignment process logic.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described primarily in the context of a hybrid fibercoax (HFC) cable architecture having a multiple systems operator (MSO),digital networking capability, IP delivery capability, and a pluralityof client devices/CPE, the general principles and advantages of thedisclosure may be extended to other types of distributed networks andarchitectures that are configured to deliver digital e.g., media data(e.g., text, video, and/or audio) or other data. Such other networks orarchitectures include optical, wired, and/or wireless elements, thefollowing therefore being merely exemplary in nature. For instance,aspects of the present disclosure may be applied to communications orprovisioning of DU entities associated with a CU within a 3GPP 5G NR(New Radio”) system.

It will also be appreciated that while described generally in thecontext of a network providing data or content delivery services tousers or subscribers of the HFC network referenced above, the presentdisclosure may be readily adapted to other types of environmentsincluding, e.g., commercial/enterprise, and government/militaryapplications, and/or other types of internetworks. Myriad otherapplications are possible.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, InternetProtocol DARPA Internet Program Protocol Specification, IETF RCF 791(Sept. 1981) and Deering, et al., Internet Protocol, Version 6 (IPv6)Specification, IETF RFC 2460 (December 1998) each of which isincorporated herein by reference in its entirety) and the associatedTransport Control Protocol (TCP), it will be appreciated that thepresent disclosure may utilize other types of protocols (and in factbearer networks to include other internets and intranets) to implementthe described functionality.

Moreover, while the exemplary aspects of the disclosure are describedprimarily with respect to the “Remote PHY” variant of theDistributed-CCAP (D-CCAP) architecture of the relevant standards andspecifications, it will be appreciated that these aspects may be readilyadapted by those of ordinary skill, given the present disclosure, toother ones of the D-CCAP architecture(s) (including for instance the“Remote MAC+PHY” variant).

Lastly, it is noted that while a certain scheme or model (e.g., OSImodel, Layers 1, 2, 3, etc.) for network layering or construction arereferenced herein, the various aspects of the disclosure are in no waylimited to such descriptions, models or schemes.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Management and Configuration of the RPD

In the above-mentioned DDA model, the exemplary Remote PHY Device or RPDand CCAP Cores communicate using a variety of protocols carried over IP.It is noted in passing that while the current specification describes a“Remote PHY Device”, it is also possible to include other DOCSISfunctions in the remote device (e.g. the DOCSIS MAC protocol functions),and hence more generic “Remote or Distributed Communications Devices” orRDCDs may be used consistent with the various aspects of the presentdisclosure, the RPDs being one exemplary species thereof.

As previously noted, communication between an exemplary CCAP Core entityand the RDCDs (e.g., RPDs), including during the RPD Initializationprocess, is set forth in Cable Labs specification “Data-Over-CableService Interface Specifications DCA—MHAv2 Remote PHY SpecificationCM-SP-R-PHY-I06-170111,” incorporated herein by reference in itsentirety (hereinafter “CM-SP-R-PHY-I06-170111”). The initializationprocess comprises, inter alia, the steps that the RPD executes afterpowering up to becoming fully operational. These steps includingfunctions such as authenticating to the network (i.e., that the RPD isin fact a valid RPD), obtaining an IP address (e.g., IPv4 or IPv6),obtaining the IP addresses of the CCAP Core entity or entities withwhich it communicates, and establishing the necessary connections orsessions to the CCAP Core(s).

Referring now to FIG. 3, one embodiment of a CCAP-based architectureaccording to the present disclosure is shown and described.Specifically, the architecture 300 of FIG. 3 provides, inter alia,facility for RPD and enhanced RPD (eRPD) data discovery by the enhancedCCAP Core (eCore) 302, and configuration of eRPDs 304 includingassignment/re-assignment to one or more CCAP eCores 302 (and/ornon-enhanced CCAP Cores 202). In the present context, the terms “eCore”and “eRPD” refer generally and without limitation to CCAP Core and RPDentities or processes, respectively, which have been enhanced with thevarious functions and capabilities for configuration, redirection, andassignment/re-assignment according to the present disclosure. Forexample, in one exemplary variant, the eCore implements a subset of thefunctionality of a Principal Core (e.g., only what is necessary toconfigure an redirect an RPD/eRPD), as well as the additional logicrepresented by inter alia, FIG. 7 herein that support interactions withthe installer, handling RPD reboot cases, etc. It will be appreciatedthat these enhanced entities or components can be combined into anetwork architecture with non-enhanced components (i.e., in aheterogeneous configuration), depending on the particular desiredattributes and state of deployment of the host distributed network.

Several operational considerations and/or use cases for assigning eRPDsor RPDs with a given eCore/Core entity (or set of eCore/Core entities)will be recognized. For example, an MSO or operator may want to assignan RPD/eRPD to a CCAP Core/eCore based on: (i) the make, model, serialnumber and/or software version of the RPD/eRPD; (ii) the location of theRPD/eRPD; (iii) the unique MAC address of the RPD/eRPD; (iv) anoperator-assigned identifier (e.g., an alias or opaque variable), suchas to create logical groupings of RPDs/eRPDs; and/or (v) a combinationof information about the RPDs/eRPDs, the state of the CCAP Cores/eCores(e.g., the number of currently assigned RPDs/eRPDs per Core/eCore),other systems and external data (e.g. time of day), etc.

The present embodiment comprises, inter alia, a set of systems,apparatus, and methodologies to configure an RPD/eRPD (or more broadlyan RDCD/eRDCD), and redirect it to one or more CCAP Core/eCore entities,based on a prescribed set of rules and/or data.

Referring again to FIG. 3, the exemplary eRPD and a given CCAP eCorecommunicate via three (3) different interfaces carried via the IPnetwork layer protocol: (i) R-DEPI, (ii) R-UEPI, and (iii) GCP aspreviously described herein. Particularly, the GCP is utilized byexemplary embodiment of FIG. 3 to both (i) read information about theparticular RPD/eRPD 304, and (ii) write configuration information andother data into the RPD/eRPD. These functions are necessary toperformance of the assignment on an RPD/eRPD to one or more CCAPCores/eCores 302 by the Analytics Assignment Engine (AAE) 307 asdescribed in greater detail below.

Also shown in FIG. 3 is an optional assignment analytics engine 307,which in the exemplary configuration comprises one or more algorithmicprograms or routines in data communication with the eCore 302 (includingbeing disposed thereon, or distributed among multiple logical processingentities of the host cable or other network) configured to obtain theaforementioned data (i)-(v) and optimize assignment of the RPDs/eRPDs toeCores within the network, whether as a whole or based on analysis ofonly portions of the network (e.g., logical or geographic portions ofthe network topology).

In the illustrated embodiment, the architecture 300 of FIG. 3 is alsoconfigured to communicate with one or more mobile devices 317 (andprocesses running thereon), such as via an interposed wireless WLAN,cellular, or WMAN infrastructure, as described in greater detailsubsequently herein. As such, the mobile device processes may alsocomprise part of the aforementioned analytics and assignment engine 307,such as by obtaining (and even pre-processing or calculating) variousparameters relating to the RPD/eRPD installation/configuration process,and providing such parameter data back to the eCore 302 and/or engine307.

It will be appreciated that various core “types” as specified byCM-SP-R-PHY-I06-170111 may be used consistent with the various aspectsof the present disclosure. Core types are defined byCM-SP-R-PHY-I06-170111 to be either Principal or Auxiliary. An RPD/eRPDcan be connected to multiple CCAP Cores/eCores. Each CCAP Core/eCoremanages and configures an independent subset of the RPD resources; e.g.,one or more RF channels. A Principal Core is responsible for theconfiguration of common parameters for the RPD (e.g., downstream powerlevel), and for certain device management functions. Auxiliary Cores areresponsible for providing other functions or services; e.g., DOCSIS,video, or OOB services, and are restricted to a resource set assigned tothem by the cognizant Principal Core. An RPD must complete itsconfiguration with the cognizant Principal Core before allowingconfiguration or re-configuration from an Auxiliary Core. Likewise, agiven RPD must perform configuration from only one Principal Core.

Furthermore, a Principal Core can redirect an RPD (see Section 6.6.2.6of CM-SP-R-PHY-I06-170111), including under instances where: (i) aPrincipal Core does not have configuration data for an RPD, or (ii) theCore is not aware of the RPD. In such cases, the Core can either rejectthe connection and log an error, or use the aforementioned GCP interfaceto redirect the unknown/unconfigurable RPD to another Core.

Accordingly, in the exemplary embodiment of the architecture 300 of FIG.3, the concept of redirection is utilized to designate the eCore 302 asa “default” or fallback Principal Core, which can use data and rulesembodied in the AAE algorithms/engine 307 to determine which“operational” Principal Core/s an RPD should be assigned to. The“default” eCore in one variant only implements the subset of PrincipalCore functions which are necessary to determine correct operationalCore(s), and to redirect the RPDeRPD to it/them.

Generally, in order to set up the communication session between a CCAPCore and an RPD, the RPD must go through an initialization process asdescribed in CM-SP-R-PHY-I06-170111. The steps are shown in the logicalflow chart 400 of FIG. 4 herein. The specific steps for connection to aPrincipal Core are also described in CM-SP-R-PHY-I06-170111, shown inthe process 500 of FIG. 5 herein.

Once an RPD connects to a CCAP Core, it creates a connection via the GCPinterface. After establishing a TCP connection, the RPD sends an NTF(notification) message to the CCAP

Core, in order to allow the CCAP Core to identify the RPD. A number ofTLVs are included in initial notification message sent by the RPD.Specifically, see Table 1 below:

TABLE 1 TLV Name Value VendorName, 50.19.1 VendorId, 50.19.2ModelNumber, 50.19.3 DeviceMacAddress, 50.19.4 CurrentSwVersion, 50.19.5BootRomVersion, 50.19.6 DeviceDescription, 50.19.7 DeviceAlias, 50.19.8SerialNumber, 50.19.9 RpdRcpProtocolVersion, 50.19.14RpdRcpSchemaVersion, 50.19.15 DeviceLocation, 50.24

Per CM-SP-R-PHY-I06-170111, based on the received information in theinitial NTF message, a given CCAP Core can redirect the RPD to anotherCCAP Core (or a set of CCAP Cores) by sending to the RPD an IRA messagewith the RpdRedirect TLV (the latter which includes an ordered list ofIP addresses of CCAP Cores). When the RPD receives such redirectrequest, it sends a response to the IRA message, and disestablishes theTCP connection to the redirecting CCAP Core. It then attempts to connectto the CCAP Core to which it is redirected.

CM-SP-R-PHY-I06-170111 further specifies that the CCAP core can delaythe redirection for up to 60 secs., which is related to the timeoutvalues specified for cases where a failure occurs (Section 6.6.2.5) orotherwise.

The Default CCAP Core must establish itself as the RPD's Principle Coreso that it may use GCP to write certain configuration information intothe RPD (e.g. DeviceAlias) before redirecting to an Operational Core.Hence, this requirement allows an RPD/eRPD installer in the presentdisclosure to configure these values at the time of installation. As abrief aside, the terms “installation” and “installer” as used herein areintended to refer to either or both of (i) an at least partly manualinstallation process, such as one conducted by one or more humans usinge.g., application software executing on a mobile device operatingsystem, and/or (ii) an automated or semi-automated computer program orprocess configured to execute to implement the installation process. Forexample, the installer may be a human using a software equipped mobiledevice, the software communicative with a back-end or network-basedprocess (e.g., running on an MSO server) for communication of datarelating to RPD/eRPD configuration. Alternatively, the installer maycomprise only the automated or semi-automated back-end process operativeto communicate data with the target RPD/eRPD via e.g., an applicationprogram or firmware installed on the RPD/eRPD and a wireline or wirelessinterface of the RPD/eRPD. For example, the RPD/eRPD may be part of aLAN, WLAN, WMAN, etc. such that the network installation process cancontact it via such interposed networks and data interfaces, such as viaTCP/IP protocols Ethernet protocols, or otherwise. As yet anotheralternative, the installer may comprise a process (e.g., software orother) wholly resident on the PRD/eRPD and configured to execute under aprescribed set of circumstances; e.g., only on initial startup, reboot,upon receipt of an external command, or other.

Per CM-SP-R-PHY-I06-170111, the steps for a CCAP Core to establishitself as a “Principle Core” are specified in Section 11.2 RPD “Startupwith Multiple Cores,” and generally include: (i) GCP TCP sessionestablishment; (ii) the Principal CCAP Core writing its IP address intothe ActivePrincipalCore object of the target RPD before attempting anyother GCP write operations. Information configured into the RPD by theDefault CCAP Core/eCore will persist after reboot/restart of theRPD/eRPD, and may include a number of TLVs or other parameters.Specifically, the Device Alias is a TLV that indicates a device nameassigned by the network operator via management interface. This objectis an ‘alias’ name for the RPD/eRPD device, and provides a non-volatilenomenclature for the RPD/eRPD.

The AssetId comprises a data string identifying the revision of theRPD/eRPD hardware, and is modeled after entPhysicalAssetID objectdefined in RFC 6933.

The Device Location Description object allows the RPD/eRPD to inform theCCAP Core about it its location. The format of the information isspecific to an MSO or other operator.

The GeoLocationLatitude and DeviceGeoLocationLongitude objects allow theRPD/eRPD to inform the CCAP Core/eCore about the latitude and longitudeportions of its geographic location, respectively.

After the Default CCAP Core completes configuration of the RPD/eRPD withthe necessary information to derive the correct Operational Core/eCore,it can use the GCP protocol to reboot/reset the RPDeRPD, and thenredirect the RPD/eRPD to the correct operational core during thesubsequent GCP initialization attempt to the Default CCAP Core/eCore.Alternatively, the Default Core/eCore can use GCP to redirect theRPD/eRPD without the additional reboot/restart if the RPD/eRPD acceptsthe redirection configuration from the Default Core/eCore.

First Exemplary Implementation

Referring now to FIGS. 7-10, a first exemplary implementation of thevarious aspects of the disclosure set forth above is described indetail. In this implementation, operators of the DHCP system used by theRPDs/eRPDs are configured with the IP address of the Default CCAPCore/eCore as the Principal Core (i.e., in DHCP Suboption 61).

As previously discussed, when an RPD/eRPD is powered on, it boots andstarts an initialization process including network authentication andaddress assignment via DHCP. In this implementation, the RPD/eRPD usesthe Principal Core addresses in Suboption 61 of the DHCP response toestablish communications with the Default CCAP Core/eCore. The DefaultCCAP Core/eCore will process the RPD/eRPD communication attempt as shownin the flow chart of FIG. 7. It will be appreciated that as used in FIG.7 and other FIGS. Thereafter, the terms “RPD” and “Core” are meant toinclude either or both of enhanced RPDs (eRPDs) and non-enhanced RPDs,and enhanced Cores (eCores) and non-enhanced Cores, respectively, asapplicable.

Referring again to FIG. 7, steps 702-706 of the process 700 complete themutual authentication, establish the GCP interface, and process theRPD/eRPD Notify message. When ready for redirect (step 708), theOperational Core is determined (step 710) and the RPD/eRPD redirectedthereto, and notification provided to the installer (steps 714-716). Ifno Operational Core is/can be determined, the connection is refused andan error logged per step 712.

Alternatively, in the case where the RPD/eRPD is not ready for redirect,the Default Core/eCore sets itself as the “Active Principal Core” in theRPD/eRPD, and notifies the installer that RPD is available to beconfigured per steps 718-720. Once configuration data is obtained fromthe installer per step 722, the RPD/eRPD software may be updated perstep 724 and step 734, or alternatively the RPD/eRPD is then configured,the Operational Core determined, and the RPD/eRPD marked as ready forredirect per steps 726-730. Under either prong (software update/nosoftware update), the RPD/eRPD is then rebooted (see e.g., step 732).

Alternatively, if the RDP/eRDP supports a redirection post-configurationvia the GCP interface, the process is as shown in FIG. 8. Specifically,steps 802-806 of the process 700 complete the mutual authentication,establish the GCP interface, and process the RPD/eRPD Notify message.The Default Core/eCore sets itself as the “Active Principal Core” in theRPD/eRPD per step 808, and notifies the installer that RPD is availableto be configured per step 810. Once configuration data is obtained fromthe installer per step 812, the RPD/eRPD software may be updated perstep 814 and step 816, or alternatively the RPD/eRPD is then configured,the Operational Core determined, and the RPD/eRPD marked as ready forredirect per steps 818-822. Under either prong (software update/nosoftware update), the RPD/eRPD is then rebooted (see e.g., step 824).

In either scenario, the RPD installer can make use of a portable ormobile computing device or distributed processes to receivenotifications or check the state of the RPD/eRPD processing by theDefault CCAP Core/eCore. Moreover, the installer can use such portableor mobile computing devices or distributed processes to provide theDefault CCAP Core with certain configuration data (e.g. Device Alias,Device Location Description, GeoLocationLatitude,DeviceGeoLocationLongitude, AssetId, etc.). Depending on configuration,the installer can manually enter this data using the portable/mobiledevice (i.e., via the UI of the device), generate some of the data usingthe device's capabilities (e.g. GPS receiver), and/or use the device toacquire some of the data from other systems (e.g. web service forgenerating AssetIds) via wireless interface of the mobile device.Alternatively, where the installer comprises a computerized process(e.g., one operative to run on a designated server or other platformwhich can access the RDP/eRPD being “installed,” this process can obtainthe relevant data for provision to the RPD/eRPD via one or morenetworked sources (e.g., from an MSO LAN, external webserver, etc.).

After the RPD installer has provided configuration data the Default CCAPCore/eCore can also command the RPD to initiate a secure software updatebased on data and rules. After the upgrade is completed, the RPD/eRPDwill reboot and will be processed per the above processes flows.

In the exemplary implementation, determination (identification) of theOperational Core includes obtaining data from external systems (e.g.,via data “push” or “pull”), or via manual entry by an MSO or othersystems operator via an administration data interface. The obtained datais also processed, and related calculations based on a set of rules orprogrammatic logic (e.g. computer programs, scripts, etc.) are made. Inone variant, eCore/eRPD assignments that implement a topology that isconsistent with or embodies the overall network topology, or specifictopological policies, is calculated. For example, under one approach,all the RPDs/eRPDs serving a specific five-block geographic area areassigned to a set of CCAP Cores/eCores located in a specific data centerand running a specific version of the CCAP code. Similarly, all theRPDs/eRPDs serving subscribers connected to a specific distribution hubmay be assigned to a set of CCAP Cores/eCores located in a specific datacenter and running a specific version of CCAP code.

In another variant, a network operator may want to set a policy thatassigns RPDs/eRPDs serving a specific distribution hub across two datacenters (i.e., an “active-active” topology). If one set of servingCores/eCores failed for whatever reason, only half of the RPDs/eRPDswould have to be re-assigned. This approach in effect allows operatorsto enforce failure group size policies for RPDs/eRPDs and CCAPCores/eCores by including such data as a parameter within the policyassignment calculation.

The Default CCAP Core/eCore can be configured with logical groupings ofone or more Operational CCAP Cores/eCores, with such groupings reflectedin e.g., data structures such as files. Furthermore, each groupingand/or individual core in the grouping and be configured with associatedmetadata. These logical groupings and associated metadata can be usedfor example in the calculation of the correct Operational Core to whichto redirect the RPD. Specifically, as referenced above, the logicalgroupings of Cores/eCores are part of the overall network topology. Forexample, a network operator may want all the RPDs/eRPDs servicing aparticular set/subset of subscribers connected via a prescribed hub(e.g., HUB-A) assigned to a particular set of Cores. Furthermore, forperformance reasons, the RPDseRPDs may need to be distributed acrossmultiple Core instances. Therefore, the operator may define a logicalgrouping—e.g., of N Cores—for that HUB-A. Each Core would have metadata(or other data) associated with it that allows the network policy engine(e.g., the analytics engine 307 of FIG. 3 herein) to calculate theassignment based on the desired topology. Each Core may also beconfigured with metadata or other ancillary data, such as for example alist of street addresses that it supports, or a logical name. When theinstaller sets up a given RPD/eRPD, they/it can configure theDeviceAlias thereof to include one of the assigned logical names. Thepolicy engine 307 may then match that RPD/eRPD location or theDeviceAlias to the metadata to determine the assignment.

The foregoing mechanisms can be used for a variety of functions,including for instance to enable operational features, describe oridentify behaviors, support load balancing of RPDs/eRPDs across agrouping of Operational Cores/eCores, or for identification/response ofpredetermined fail-over behaviors. As but one example, FIG. 9illustrates a logical grouping of Operational CCAP Cores/eCores andassociated metadata according to the disclosure. As shown, the logicalgrouping configuration 900 includes two logical groups 902, 904 (groupedaccording to association with Hub A and Hub B, respectively), each withtwo or more core instances 906, 908 (e.g., Core 1 and Core 2 associatedwith Hub A and Hub B, respectively). Each core instance 906, 908includes multiple individual cores 910, including e.g., a Principal Coreand one or more Auxiliary Cores as shown. Metadata may include forexample data indicative of the function of each Core (e.g., BroadcastQAM), and IP address. In one implementation, the IP address of a givenCore/eCore is derived from the output of the above-described assignmentcalculation(s); a list of operational cores is returned to the RPD/eRPDsduring the redirect process.

FIG. 10 herein illustrates an overall system view of the architecture1000 of the exemplary implementation described with respect to FIGS.7-9, including the Default CCAP Core/eCore 1002, external system(s)1004, and Operational CCAP Core/ECore(s) 1005, and their relationship tothe RPD/eRPD(s) 1006.

Second Exemplary Implementation

Referring now to FIGS. 11-13, a second exemplary implementation of thevarious aspects of the disclosure set forth above is described indetail. In this implementation, an operational process that supportsRPDs/eRPDs that do not require additional configuration data from theinstaller is included. For example, the RPD/eRPD may have an embeddedGPS receiver, and/or the Default CCAP Core/eCore uses data from externalsystems to determine or create any necessary configuration data (e.g.Device Alias, Device Location Description, GeoLocationLatitude,DeviceGeoLocationLongitude, AssetId, etc.). In the exemplary case of theRPD/eRPD having an embedded GPS capability, the Default CCAP Core canuse data from external systems (and/or data manually entered by theoperator via the aforementioned administrative data interface) todetermine or create the relevant parameters or IDs for a given RPD/eRPD,such as the Device Alias, Device Location Description, etc., based on aset of rules or programmatic logic (e.g. computer programs, scripts).This implementation also includes the functionality of notifying theinstaller (and/or an administrator) of the status of configurationprocessing for the given RPD/eRPD.

As with the first implementation, operators of the DHCP system used bythe RPDs/eRPDs are configured with the IP address of the Default CCAPCore/eCore as the Principal Core (i.e., in DHCP Suboption 61). TheDefault CCAP Core/eCore will process the RPD/eRPD communication attemptas shown in the flow chart of FIG. 11. Specifically, as shown, steps1102-1106 of the process 1100 complete the mutual authentication,establish the GCP interface, and process the RPD/eRPD Notify message.When ready for redirect (step 1108), the Operational Core is determined(step 1110) and the RPD/eRPD redirected thereto, and notificationprovided to the installer (steps 1116-1118). If no Operational Coreis/can be determined, the connection is refused and an error logged perstep 1112, and the installer notified per step 1114.

Alternatively, in the case where the RPD/eRPD is not ready for redirect,the Core/eCore sets itself as the “Active Principal Core” in theRPD/eRPD per step 1120. If the RPD requires configuration data from theinstaller per step 1122, the installer is notified that the RPD/eRPD isavailable to be configured per step 1124. Once configuration data isobtained from the installer per step 1126, the RPD/eRPD is thenconfigured, the Operational Core determined, and the RPD/eRPD marked asready for redirect per steps 1128-1132. If a software update is requiredper step 1134, the installer is notified per step 1140 and a commandissued to cause the RPD/eRPD to upgrade per step 1142. If no softwareupgrade is required, the RPD/eRPD is rebooted and the installer (and/oradmin. process) notified per steps 1136-1138.

Alternatively, if the RDP/eRDP supports a redirection post-configurationvia the GCP interface, the process is as shown in FIG. 12. Specifically,steps 1202-1206 of the process 1200 complete the mutual authentication,establish the GCP interface, and process the RPD/eRPD Notify message.The Core/eCore sets itself as the “Active Principal Core” in theRPD/eRPD per step 1208, and then per step 1210, if the RPD/eRPD requiresconfiguration data from the installer, notifies the installer thatRPD/eRPD is available to be configured per step 1212. Once configurationdata is obtained from the installer per step 1214, the RPD/eRPD softwaremay be updated per steps 1216, 1226 and 1228, or alternatively theRPD/eRPD is then configured, the Operational Core determined, theRPD/eRPD redirected to the Operational Core, and the installer and/oradmin. process notified of the redirection per steps 1218-1224.

FIG. 13 herein illustrates an overall system view of the architecture1300 of the exemplary implementation described with respect to themethodologies of FIGS. 11-12.

FIG. 9 discussed above illustrates an exemplary logical grouping ofOperational CCAP Cores/eCores and associated metadata useful with theimplementation of FIGS. 11-13.

Third Exemplary Implementation

Referring now to FIG. 14, a third exemplary implementation of thevarious aspects of the disclosure set forth above is described indetail. In this implementation, an operational process is included thatsupports RPDs/eRPDs that do not require additional configuration datafrom the installer (and which can be redirected in less than the60-second timeout period described in the Cable Labs MHAv2 Remote PHYSpecification CM-SP-R-PHY-I06-170111 previously incorporated herein.Specifically, CM-SP-R-PHY-I06-170111 states at Section 6.6.2.6 that if aPrincipal CCAP Core does not have configuration data for an RPD (or isnot aware of the RPD), the core should either reject the connection andlog an error, or use GCP to redirect the RPD to another core. Moreover,a CCAP Core can elect to redirect (via GCP) an RPD to one or morealternate CCAP Cores for further configuration, such as to act as astandby or to provide additional services. The redirecting CCAP Coretransfers a variable length list of IPv4/IPv6 addresses to the RPD, butcan delay providing the redirect information to the RPD for a period ofup to 60 seconds.

Hence, in this third implementation, the Default CCAP Core/eCore wouldagain not have to designate itself as the Primary CCAP Core. Forexample, the RPD/eRPD may have an embedded GPS receiver, and/or theDefault CCAP Core/eCore uses data from external systems to determine orcreate any necessary configuration data (e.g. Device Alias, DeviceLocation Description, GeoLocationLatitude, DeviceGeoLocationLongitude,AssetId, etc.). In the exemplary case of the RPD/eRPD having an embeddedGPS capability, the Default CCAP Core can use data from external systems(and/or data manually entered by the operator via the aforementionedadministrative data interface) to determine or create the relevantparameters or IDs for a given RPD/eRPD, such as the Device Alias, DeviceLocation Description, etc., based on a set of rules or programmaticlogic (e.g. computer programs, scripts). This implementation alsoincludes the functionality of notifying the installer (and/or anadministrator) of the status of configuration processing for the givenRPD/eRPD.

As with the first implementation, operators of the DHCP system used bythe RPDs/eRPDs are configured with the IP address of the Default CCAPCore/eCore as the Principal Core (i.e., in DHCP Suboption 61). TheDefault CCAP Core/eCore will process the RPD/eRPD communication attemptas shown in the flow chart of FIG. 14. Specifically, as shown, steps1402-1406 of the process 1400 complete the mutual authentication,establish the GCP interface, and process the RPD/eRPD Notify message.

If a software update is required or to be conducted per step 1408, theinstaller is notified per step 1418 and a command issued to cause theRPD/eRPD to upgrade per step 1420. If no software upgrade is required orto be conducted, the RPD/eRPD is configured per step 1410, and theOperational Core/eCore determined per step 1412. The RPD/eRPD is thenredirected to the Operational Core per step 1414, and the installer(and/or admin. process) notified per step 1416.

FIG. 9 illustrates an exemplary logical grouping of Operational CCAPCores/eCores and associated metadata useful with the methodology of FIG.12.

Fourth Exemplary Implementation

Referring now to FIGS. 15A and 15B, a fourth exemplary implementation ofthe various aspects of the disclosure set forth above is described indetail. This implementation is useful with, inter alia, all the previousimplementations described above, and includes the ability of theexternal system(s) 1504 used by the Default CCAP to interact with thesystems used to manage the Operational CCAP Cores/eCores 1505. Thisfunctionality allows the Default CCAP Core/eCore 1502 to identify thecurrent state of the Operational CCAP Cores/eCores and the associatedRPDs/eRPDs 1506, which can be used in the process to identify theOperational CCAP Core to which to assign a given RPD/eRPD. This processcan include obtaining and using information about the operational stateof a given Operational CCAP Core/eCore, the number of RPDs/eRPDscurrently assigned to a given Operational CCAP Core/eCore, the versionof hardware or software of a given Operational CCAP Core/eCore, and/orother information about the Operational CCAP Core/eCore 1505 that may beuseful to the state analysis and assignment process.

In the exemplary embodiment, the interaction between the externalsystem(s) used by the Default CCAP Core/eCore and the systems 1510 usedto manage the Operational CCAP Cores is subscribe/notify based, althoughother approaches such as query/response may be used. The formeradvantageously allows the external system(s) used by the Default CCAPCore/eCore to receive unsolicited updates when a given Operational CCAPCore/eCore 1505 changes state or configuration.

Furthermore, in the case where Operational CCAP Cores/eCores areimplemented as functions in a virtualized computing environment, theexternal system(s) used by the Default CCAP Core/eCore to interact withthe systems used to manage the Operational CCAP Cores/eCores can invokea software process that results in the Operational CCAP Core'smanagement systems 1510 creating new instances of an Operational CCAPCore/eCore (such as for example in an object-oriented environment suchas Java). This can advantageously allow for flexible scaling ofOperational CCAP Cores/eCores based on, e.g., the rate of RDPs/eRPDsrequesting assignment via the Default CCAP Core (as reflected by thedashed line 1512 in FIG. 15B).

It will further be appreciated that the Default CCAP Core/eCore 1502 canalso be implemented as functions in a virtualized computing environment(similar to the Operational Core/ECore(s) 1505), and hence scale up ordown instances as need to handle the rate of RDPs/eRPDs requestingassignment via the Default CCAP Core/eCore 1502.

FIG. 15B illustrates an overall system view of the architecture of thefourth exemplary implementation described above with respect to FIG.15A.

Exemplary Analytic Engine Calculations

FIG. 16 is a graphical representation of an exemplary embodiment of ananalytics engine calculation of the type previously referenced herein;i.e., for Core/eCore-to-RPD/eRPD allocation and/or topologydetermination.

In the illustrated embodiment, the process 1600 includes first obtainingRPD/eRPD logical identifiers, location information, and/ordevice-specific information as described previously from the pool ofRPDs/eRPDs participating in the allocation/calculation. This may be asas few as a single RPD/eRPD, or several.

Next, based on an order of evaluation, the RPD/eRPDidentifiers/information previously obtained is used to generate a listof Cores/eCores that match, or are consistent with, thoseidentifiers/information. For instance, in one variant, a search/matchfunction is used to search relevant portions of Core/eCore data for anexplicit match to one or more data items. Alternatively, more heuristicor non-deterministic approaches to selection may be used, such as fuzzylogic variables, scoring, minimum thresholds, etc.

Next, the generated list of Cores/eCores is filtered based on theCore/eCore Operational Data (e.g., status such asactive/inactive/non-operational, etc.).

One or more failure group size rules (or other rules such as loadbalancing) are then applied to the filtered list, and the final list ofCore(s)/eCore(s) selected. For example, if the list of activeCores/eCores includes entities that are located across multiple datacenters, the Cores/eCores from a single datacenter are selected suchthat the RPDs/eRPDs are evenly distributed across the data center(s),such as to achieve desired failure mitigation or containment, loadbalancing across different data centers, etc.

If the aforementioned calculation by the analytics engine 307 yields noviable Cores/eCores, then the Core OSS systems are notified (such as viaa protocol message) of the failure. In one variant, this notificationinstigates the OSS (or its proxy entity or entities) to remediate, suchas bringing one or more new Cores/eCores on line. In one implementation,the notification message from the analytics engine 307 also includesfailure data or codes, indicative of the cause of the failure or thestep of the process where the result converged to null. For instance, ifthe generated list did not survive filtration, then remediation actionsinstituted by the OSS may be different than if the null result wasachieved on another step of the process.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

1.-18. (canceled)
 19. A method of operating a computerized networkapparatus within a Data Over Cable Service Interface Specification(DOCSIS)-compliant and Converged Cable Access Platform (CCAP)Distributed Access Architecture (DAA)-compliant hybrid fiber coax (HFC)network to configure one or more computerized devices with a topology ofthe HFC network, the method comprising; obtaining a first plurality ofdata relating to a plurality of remote physical layer devices within theHFC network; obtaining a second plurality of data relating to aplurality of core entities within the HFC network; executing at leastone algorithm to process the first data and the second data, and thirddata relating to one or more network configuration rules orrequirements, the executing at least in part calculating a topology forthe HFC network; and causing allocation of at least a portion of theplurality of remote physical layer devices to respective one or more ofthe plurality of core entities based at least on the calculatedtopology.
 20. The method of claim 19, wherein the obtaining a firstplurality of data relating to a plurality of remote physical layerdevices comprises obtaining a first plurality of data relating to eachof a plurality of a CCAP-compliant Remote PHY (Devices (RPDs).
 21. Themethod of claim 19, further comprising: receiving policy-related datafrom an operator or management process of the HFC network; and executingthe at least one algorithm to further process at least a portion of thereceived policy-related data for said calculating of the topology. 22.The method of claim 21, wherein: the receiving policy-related datacomprises receiving data correlating at least a portion of the pluralityof remote physical devices to a prescribed geographic area; and thecausing allocation comprises assigning the at least portion of theplurality of remote physical devices correlated to the prescribedgeographic area to one or more CCAP Cores or CCAP eCores of a prescribednetwork data center and operative to execute a prescribed version of aCCAP software or firmware.
 23. The method of claim 19, wherein: theobtaining a first plurality of data relating to a plurality of remotephysical layer devices within the HFC network comprises receiving datacorrelating at least a portion of the plurality of remote physicaldevices to a prescribed geographic area; and the causing allocationcomprises assigning the at least portion of the plurality of remotephysical devices correlated to the prescribed geographic area to one ormore CCAP Cores or CCAP eCores of a prescribed network data center andoperative to execute a prescribed version of a CCAP software orfirmware.
 24. The method of claim 19, wherein: the obtaining a firstplurality of data relating to a plurality of remote physical layerdevices within the HFC network comprises receiving data correlating atleast a portion of the plurality of remote physical devices to one ormore prescribed network distribution hubs; and the causing allocationcomprises assigning the at least portion of the plurality of remotephysical devices correlated to the one or more prescribed network hubsto one or more CCAP Cores or CCAP eCores of a prescribed network datacenter and operative to execute a prescribed version of a CCAP softwareor firmware.
 25. The method of claim 19, wherein: the obtaining a firstplurality of data relating to a plurality of remote physical layerdevices within the HFC network comprises receiving data correlating atleast a portion of the plurality of remote physical devices to one ormore prescribed network distribution hubs; and the causing allocationcomprises assigning the at least portion of the plurality of remotephysical devices correlated to the one or more prescribed network hubsacross two or more network data centers.
 26. The method of claim 25,further comprising: detecting failure of at least one core entityassociated with one of the two or more network data centers; and basedat least in part on the detecting, causing reassignment of a subset ofthe at least portion of remote physical devices to another of the two ormore data centers.
 27. The method of claim 26, further comprisingreceiving policy data specifying at least one of a desired failure groupsize or maximum failure group size; and wherein the assigning the atleast portion of the plurality of remote physical devices correlated tothe one or more prescribed network hubs across two or more network datacenters comprises causing the assigning so as to obey the specified atleast one of the desired failure group size or maximum failure groupsize.
 28. Computerized network apparatus, comprising: digital processorapparatus; at least one data interface in data communication with thedigital processor apparatus; and at least one storage device in datacommunication with the digital processor apparatus, the at least onestorage device comprising a storage medium having at least one computerprogram disposed thereon, the at least one computer program configuredto, when executed, cause the computerized network apparatus to: obtain afirst plurality of data relating to a plurality of remote physical layerdevices within a hybrid fiber coax (HFC) network, the HFC networkcomprising a Data Over Cable Service Interface Specification(DOCSIS)-compliant and Converged Cable Access Platform (CCAP)Distributed Access Architecture (DAA)-compliant network; obtain a secondplurality of data relating to a plurality of core entities within theHFC network; execute at least one algorithm to process the first dataand the second data, and third data relating to one or more networkconfiguration rules or requirements, the execution at least in partcausing calculation of a topology for at least a portion of the HFCnetwork; and cause allocation of at least a portion of the plurality ofremote physical layer devices to respective one or more of the pluralityof core entities based at least on the calculated topology.
 29. Computerreadable apparatus comprising at least one storage medium, the at leastone storage medium comprising at least one computer program, the atleast one computer program comprising a plurality of instructions which,when executed on a computerized device: obtain a first plurality of datarelating to a plurality of remote physical layer devices within adistributed architecture digital network, the distributed architecturedigital network comprising a Data Over Cable Service interfaceSpecification (DOCSIS) compliant and Converged Cable Access Platform(CCAP) Distributed Access Architecture (DAA) compliant hybrid fiber coax(HFC) network; obtain a second plurality of data relating to a pluralityof core entities within the distributed architecture digital network;execute at least one algorithm to process the first data and the seconddata, and third data relating to one or more network configuration rulesor requirements, to calculate a topology for the distributedarchitecture digital network; and cause allocation of at least a portionof the plurality of remote physical layer devices to respective one ormore of the plurality of core entities based on the calculated topology.